Summary

validateGatewayApiKey constructs an @ai-sdk/gateway provider with no baseURL, so the AI_GATEWAY_API_KEY check always runs against ai-gateway.vercel.sh. This forwards the AI_GATEWAY_BASE_URL environment variable to createGateway, so anyone running eve against a self-hosted or proxied AI Gateway can validate their key against the same endpoint they actually use.

const provider = createGateway({
  apiKey,
  baseURL: process.env.AI_GATEWAY_BASE_URL,
  fetch: ...,
});

createGateway already treats an undefined/empty baseURL as "use the default", so there is no behavior change when the variable is unset.

Notes

• Pairs with feat(provider/gateway): support AI_GATEWAY_BASE_URL env for the base URL ai#16401, which adds the same AI_GATEWAY_BASE_URL fallback inside @ai-sdk/gateway itself (covering the default/global provider used for runtime inference). This makes eve's own createGateway call honor it directly, without waiting on that release.
• The setup-time model-listing endpoints (gateway-models.ts / model-catalog.ts) go through vercel curl against the /v1/models API — a separate code path and endpoint — so they're intentionally left out of this change. Happy to follow up on those if desired.